Performer : Galaxy S23 Ultra

This is not something I expect, could you share a file with that so I can better understand from where it is?

Samsung model number : SM-S918B

I am not keen about having a Samsung specific field, it should be a generic field. It may be General_Encoded_Application (used for XDACM "model name") or a generic "ModelNumber".
I'll check a bit more what I have in my repository.

Android version : 14

In a similar way, maybe General_Encoded_Library_Name + General_Encoded_Application_Version is better there but I need to figure out how I manage iOS there.

Performer : Galaxy S23 Ultra

This is not something I expect, could you share a file with that so I can better understand from where it is?

Sample file from another Samsung phone here: #2175 (comment)

This one shows Performer : Samsung SM-M325FV but it should be same as one from Galaxy S23 Ultra. The video I have from S23 is not mine so cannot share.

Android version : 14

In a similar way, maybe General_Encoded_Library_Name + General_Encoded_Application_Version is better there but I need to figure out how I manage iOS there.

I got iOS sample from online which shows this:

com.apple.quicktime.make                 : Apple
com.apple.quicktime.model                : iPhone 12 Pro
com.apple.quicktime.software             : 14.1
com.apple.quicktime.creationdate         : 2020-11-06T17:19:58-0500

Offtopic, while running a local build to ensure everything still builds fine, I found that ARM builds are failing with many errors regarding WindowsNamespace::... in file winbase.h

Offtopic, while running a local build to ensure everything still builds fine, I found that ARM builds are failing with many errors regarding WindowsNamespace::... in file winbase.h

It should be resolved with an update some time ago, and we build now ARM port with VS2022 on our build farm.
If still an issue somewhere, please a dedicated ticket with details about how to reproduce the issue.

Offtopic, while running a local build to ensure everything still builds fine, I found that ARM builds are failing with many errors regarding WindowsNamespace::... in file winbase.h

It should be resolved with an update some time ago, and we build now ARM port with VS2022 on our build farm. If still an issue somewhere, please a dedicated ticket with details about how to reproduce the issue.

I'll look into and see what is going on first. Since it built fine when MediaInfo 24.12 was released, it may be broken by a Visual Studio update.

Edit: Found the cause. Setting C++20 std causes build failure for ARM64. @JeromeMartinez, the other PR needs changes.

This one shows Performer : Samsung SM-M325FV but it should be same as one from Galaxy S23 Ultra. The video I have from S23 is not mine so cannot share.

Even Samsung is not able to have a common scheme for where the model name is and where the marketing name is :).
but I guess that the S23 output is the long term one...

The "S23" stuff is in the "auth" metadata, expected to be the author/performer, not the model name, I guess I have to put check on some exception...s

For the moment I merge and I'll update it soon with a different approach for the Android version.